home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990725-20000114
/
000411_news@columbia.edu _Tue Jan 4 13:23:01 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2000-01-13
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id NAA13674
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 4 Jan 2000 13:23:01 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id NAA21206
for kermit.misc@watsun.cc.columbia.edu; Tue, 4 Jan 2000 13:02:23 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: jrd@cc.usu.edu (Joe Doupnik)
Subject: Re: MS-DOS Kermit, more capabalities
Message-ID: <Itj70WJUGaRN@cc.usu.edu>
Date: 4 Jan 00 10:39:27 MDT
Organization: Utah State University
To: kermit.misc@columbia.edu
In article <cRgc4.2429$S3.130329@tw12.nn.bcandid.com>, cangel@famvid.com writes:
> On 2000-01-01 fdc@watsun.cc.columbia.edu(FrankdaCruz) said:
>
>
> fd>: ... Most unfortunately, `Kermit' doesn't included the
> fd>: `ZMoDem' file transfer protocol (with control-character escaping
> fd>& all); : making it less than "complete", somewhat. I would
> fd>welcome postings from : people who happen to be doing fine
> fd>`ZMoDem'/`Kermit' transfers using no : more than the minimum setup
> fd>i described above. I tried a lot of packet : drivers and ~TelNet~
> fd>"shims" but nothing goes beyond D/L cps rates of a : mere 9k6/19K2
> fd>bps connection. :
>
> fd>Kermit protocol is is a fast as Zmodem if both Kermit partners
> fd>support a fairly decent implementation of it. Most
> fd>non-Kermit-Project Kermit implementations do not. Of course a 4.
> fd>77MHz CPU would also be a bottleneck but that's true for Zmodem too.
>
> Zmodem is needed for two reasons. 1) Many BBS have crippled 'clones' of
> the kermit protocol hard coded to 94 bytes per packet. As per your own
> website for Columbia Kermit the 'team' deciding to use 94 bytes as the
> default install for many years has given many the impression that kermit
> is _supposed_ to use 94 byte packets. The 'WORD' is not getting out to
> authors of BBS software. 2) Many BBS simply do not have a kermit transfer
> and the owners are not knowledgeable enough to implement the C-Kermit config
> files for an external kermit transfer (I know, I've tried and they just can't
> do it). 8(
>
> If MSKermit would allow access to it's TCP/IP stack via the 'int 14h' fossil
> interface then zmodem could be added to MSKermit as an external protocol. 8)
That is a far more complicated problem than you may realize and one
which is not desirable to solve that way.
If the BBS folks want to sell to customers using a better Kermit
protocol implementation then they can either improve their code themselves
(the specs have always been public) or they can contract someone like myself
to improve their code.
Joe D.
> Charles.Angelich
>